Proactive Energy-Aware System Software Design with SEEP
نویسندگان
چکیده
منابع مشابه
Proactive Energy-Aware System Software Design with SEEP
Designing system software currently optimizes program code for correctness and speed. While this is essential for the reliable operation of computer systems, these two characteristics alone are often not sufficient. Moreover, it is important to ensure that a third characteristic is being considered during the process of designing system software: energy efficiency. As optimizing program code fo...
متن کاملProactive Energy-Aware Programming with PEEK
Optimization of application and system software for energy efficiency is of ecological, economical, and technical importance—and still challenging. Deficiency in adequate tooling support is a major issue. The few tools available (i.e., measurement instruments, energy profilers) have poorly conceived interfaces and their integration into widely used development processes is missing. This implies...
متن کاملEnergy-Aware Programming Utilizing the SEEP Framework and Symbolic Execution
SEEP executes the code under test symbolically to extract all code paths and their path constraints. On basis of these results, SEEP crafts program code with predefined input data, so-called path entities. For each path entity, SEEP generates a runtime execution trace by executing them on a test system and increments a block counter for every basic block (branchless sequence of code) each time ...
متن کاملBattery Modeling for Energy-Aware System Design
M any features of modern portable electronic devices—such as high-speed processors, colorful displays, opti-cal/magnetic storage drives, and wireless network interfaces—carry a significant energy cost. However, advances in battery technology have not kept pace with rapidly growing energy demands. Most laptops, handheld PCs, and cell phones use rechargeable electrochemical batteries—typically, l...
متن کاملDeveloping Energy-Aware Software
ion over Component Behavior RUMs abstract over the behavior of a component, which we define as all possible execution sequences of that component. For RUMs, there are two kinds of abstraction to consider: Over-abstraction An over-abstraction (also called an overapproximation) specifies a superset of the possible execution sequences of a component. If we verify a property that holds for all exec...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Softwaretechnik-Trends
سال: 2013
ISSN: 0720-8928
DOI: 10.1007/s40568-013-0021-5